Providing product catalog software application as enterprise services

ABSTRACT

Methods and apparatus, including systems and computer program products, for a services architecture design that provides enterprise services having product catalog functionality at the level of an enterprise application. The design includes a set of service operations, process components, and optionally deployment units. Suitable business objects are also described.

BACKGROUND

This specification relates to data processing systems implemented on computers, and more particular to data processing systems providing services in the nature of web services.

Enterprise software systems are generally large and complex. Such systems can require many different components, distributed across many different hardware platforms, possibly in several different geographical locations. Thus, the architecture of a large software application, i.e., what its components are and how they fit together, is an important aspect of its design for a successful implementation.

Web services are one technology for making the functionality of software applications available to other software, including other applications. A web service is a standards-based way of encapsulating the functionality of an application that other applications can locate and access. A service-oriented architecture is a distributed software model within which functionality is defined as independent web services. Within a service-oriented architecture, web services can be used in defined sequences according to business logic to form applications that enable business processes.

SUMMARY

This specification describes a services architecture design that provides enterprise services having product catalog functionality at the level of an enterprise application. Enterprise services are web services that have an enterprise-level business value.

In its various aspects, the invention can be embodied in systems, methods, and computer program products. For example, a system in one embodiment implements a services architecture design that provides enterprise services having product catalog functionality at the level of an enterprise application. The design includes a set of service operations, process components, and optionally deployment units. Suitable business objects are also described.

The subject matter described in this specification can be implemented to realize one or more of the following advantages. Effective use is made of process components as units of software reuse, to provide a design that can be implemented reliably in a cost effective way. Effective use is made of deployment units, each of which is deployable on a separate computer hardware platform independent of every other deployment unit, to provide a scalable design. Service interfaces of the process components define a pair-wise interaction between pairs of process components that are in different deployment units in a scalable way.

Details of one or more implementations of the subject matter described in this specification are set forth in the accompanying drawings and in the description below. Further features, aspects, and advantages of the subject matter will become apparent from the description, the drawings, and the claims.

BRIEF DESCRIPTION OF THE DRAWINGS

FIG. 1 illustrates a high-level view of a software architectural design and implementation of a suite of enterprise software services having product catalog functionality.

FIGS. 2A and 2B are block diagrams collectively showing a product catalog authoring process component.

FIGS. 3A and 3B are block diagrams collectively showing a product catalog publishing process component.

Like reference numbers and designations in the various drawings indicate like elements.

DETAILED DESCRIPTION

FIG. 1 illustrates a high-level view of a software architectural design, and of application software implementations of the design, that provides a suite of enterprise service operations, which can be organized into interfaces, having product catalog application functionality.

The elements of the architecture include the business object, the process component, the service operation (or simply, the operation), the service interface, the message, and the deployment unit. The elements can also include process agents and reuse service components. These will be generally described below.

In one implementation, the software is implemented to be deployed on an application platform that includes a foundation layer that contains all fundamental entities that can used from multiple deployment units. These entities can be process components, business objects or reuse service components. A reuse service component is a piece of software that is reused in different transactions. A reuse service component is used by its defined interfaces, which can be, e.g., local APIs (Application Programming Interfaces) or service interfaces.

The architectural design is a specification of a computer software application, and elements of the architectural design can be implemented to realize a software application that implements enterprise application service interfaces. The elements of the architecture are at times described in this specification as being contained or included in other elements; for example, a process component is described as being contained in a deployment unit. It should be understood, however, that such operational inclusion can be realized in a variety of ways and is not limited to a physical inclusion of the entirety of one element in another.

The architectural elements include the business object. A business object is a representation of a type of a uniquely identifiable business entity (an object instance) described by a structural model. Processes operate on business objects.

A business object represents a specific view on some well-defined business content. A business object represents content, and instances of business objects include content, which a typical business user would expect and understand with little explanation. Whether an object as a type or an instance of an object is intended by the term is generally clear from the context, so the distinction will be made explicitly only when necessary. Properly implemented, business objects are implemented free of redundancies.

Business objects are further categorized as business process objects and, master data objects, mass data run objects, dependent objects, and transformed objects. A master data object is an object that encapsulates master data (i.e., data that is valid for a period of time). A business process object, which is the kind of business object generally found in a process component, is an object that encapsulates transactional data (i.e., data that is valid for a point in time). A mass data run object is an application object that executes an algorithm for a particular mass data run. An instance of a mass data run object contains a particular set of selections and parameters. A mass data run object implements an algorithm that modifies, manages, and/or processes a large amount of data in multiple transactions, possibly but not necessarily with parallel processing. A dependent object is a business object used as a reuse part in another business object. A dependent object represents a concept that cannot stand by itself from a business point of view. Instances of dependent objects only occur in the context of a non-dependent business object. A transformed object is a transformation of multiple business objects for a well-defined purpose. It transforms the structure of multiple business objects into a common structure. A transformed object does not have its own persistency. The term business object will be used generically to refer to a business process object and a master data object, unless the context requires otherwise. Properly implemented, business objects are implemented free of redundancies.

The architectural elements also include the process component. A process component is a software package that realizes a business process and generally exposes its functionality as services. The functionality contains business transactions. A process component contains one or more semantically related business objects. Any business object belongs to no more than one process component.

Process components are modular and context-independent. That they are context-independent means that a process component is not specific to any specific application and is reusable. The process component is the smallest (most granular) element of reuse in the architecture.

The architectural elements also include the operation. An operation belongs to exactly one process component. A process component generally has multiple operations. Operations can be synchronous or asynchronous, corresponding to synchronous or asynchronous process agents, which will be described below. An operation is the smallest, separately-callable function, described by a set of data types used as input, output, and fault parameters, or some combination of them, serving as a signature. For convenience in supporting use of the operations supported by a system implementing elements of the design, such a system can optionally include a repository of service descriptions that includes a standards-based description of each of the supported service operations.

The architectural elements also include the service interface, which may be referred to simply as an interface. An interface is a named group of operations. Each operation belongs to exactly one interface. An interface belongs to exactly one process component. A process component might contain multiple interfaces. In one implementation, an interface contains only inbound or outbound operations, but not a mixture of both. One interface can contain both synchronous and asynchronous operations. All operations of the same type (either inbound or outbound) which belong to the same message choreography will preferably belong to the same interface. Thus, generally, all outbound operations to the same other process component are in one interface.

The architectural elements also include the message. Operations transmit and receive messages. Any convenient messaging infrastructure can be used. A message is information conveyed from one process component instance to another, with the expectation that activity will ensue. An operation can use multiple message types for inbound, outbound, or error messages. When two process components are in different deployment units, invocation of an operation of one process component by the other process component is accomplished by an operation on the other process component sending a message to the first process component.

The architectural elements also include the process agent. Process agents do business processing that involves the sending or receiving of messages. Each operation will generally have at least one associated process agent. A process agent can be associated with one or more operations. Process agents can be either inbound or outbound, and either synchronous or asynchronous.

Asynchronous outbound process agents are called after a business object changes, e.g., after a create, update, or delete of a business object instance.

Synchronous outbound process agents are generally triggered directly by a business object.

An output process agent will generally perform some processing of the data of the business object instance whose change triggered the event. An outbound agent triggers subsequent business process steps by sending messages using well-defined outbound services to another process component, which generally will be in another deployment unit, or to an external system. An outbound process agent is linked to the one business object that triggers the agent, but it is sent not to another business object but rather to another process component. Thus, the outbound process agent can be implemented without knowledge of the exact business object design of the recipient process component.

Inbound process agents are called after a message has been received. Inbound process agents are used for the inbound part of a message-based communication. An inbound process agent starts the execution of the business process step requested in a message by creating or updating one or multiple business object instances. An inbound process agent is not the agent of a business object but of its process component. An inbound process agent can act on multiple business objects in a process component.

Synchronous agents are used when a process component requires a more or less immediate response from another process component, and is waiting for that response to continue its work.

Operations and process components are described in this specification in terms of process agents. However, in alternative implementations, process components and operations can be implemented without use of agents using other conventional techniques to perform the functions described in this specification.

The architectural elements also include the deployment unit. A deployment unit includes one or more process components and, optionally, one or more business objects, that are deployed together on a single computer system platform. Conversely, separate deployment units can be deployed on separate physical computing systems. For this reason, a deployment unit boundary defines the limits of an application-defined transaction, i.e., a set of actions that have the ACID properties of atomicity, consistency, isolation, and durability. To make use of database manager facilities, the architecture requires that all operations of such a transaction be performed on one physical database; as a consequence, the processes of such a transaction must be performed by the process components of one instance of one deployment unit.

The process components of one deployment unit interact with those of another deployment unit using messages passed through one or more data communication networks or other suitable communication channels. Thus, a deployment unit deployed on a platform belonging one business can interact with a deployment unit software entity deployed on a separate platform belonging to a different and unrelated business, allowing for business-to-business communication. More than one instance of a given deployment unit can execute at the same time, on the same computing system or on separate physical computing systems. This arrangement allows the functionality offered by a deployment unit to be scaled to meet demand by creating as many instances as needed.

Since interaction between deployment units is through service operations, a deployment unit can be replaced by other another deployment unit as long as the new deployment unit supports the operations depended upon by other deployment units. Thus, while deployment units can depend on the external interfaces of process components in other deployment units, deployment units are not dependent on process component interactions (i.e., interactions between process components involving their respective business objects, operations, interfaces, and messages) within other deployment units. Similarly, process components that interact with other process components or external systems only through messages, e.g., as sent and received by operations, can also be replaced as long as the replacement supports the operations of the original.

Interactions between process components that occur only within a deployment unit are not constrained to using service operations. These can be implemented in any convenient fashion.

In contrast to a deployment unit, the foundation layer does not define a limit for application-defined transactions. Deployment units communicate directly with entities in the foundation layer, which communication is typically not message based. The foundation layer is active in every system instance on which the application is deployed. Business objects in the foundation layer will generally be master data objects. In addition, the foundation layer will include some business process objects that are used by multiple deployment units. Master data objects and business process objects that should be specific to a deployment unit are preferably assigned to their respective deployment unit.

FIG. 1 illustrates a high-level view of a software architectural design and implementation of a suite of enterprise software services having product catalog functionality.

As shown in FIG. 1, a Catalog Authoring deployment unit 102 includes a Product Catalog Authoring process component 104, a Product Catalog master data object 106, a Product Catalog Update Run business object 108, a Product Catalog File Upload Run business object 110, a Product Catalog Duplication Run business object 112, a Product Catalog Change List business object 114, a Product Catalog Update Method master data object 116, and a Product Catalog Publishing Sending Run business object 120.

Additionally, as shown in FIG. 1, a Catalog Publishing deployment unit 122 includes: a Product Catalog Publishing process component 124, a Published Product Catalog master data object 126, and a Published Product Catalog Update Run business object 128.

FIGS. 2A and 2B are block diagrams collectively showing the Product Catalog Authoring process component 104 (FIG. 1). For convenience in describing this process component, a number of other process components are shown in the figures; these other process components are not part of the process component being described. These other process components are a Purchasing Contract Processing process component 202, a Product Catalog Authoring at Supplier process component 204, a Product Catalog Publishing process component 124, and a Product Catalog Authoring at Customer process component 208. These other process components are used to represent software external to the process component in describing its interactions with the external software; however, while the external software can be implemented as such process components, this is not required.

A Maintain Catalog operation 210 sends a catalog maintenance request using a Maintain Product Catalog asynchronous inbound process agent 212 to update the Product Catalog master data object 106. For example, the operation 210 can send a request to update the Product Catalog master data object 106 if input is received from the Purchasing Contract Processing process component 202 or the Product Catalog Authoring at Supplier process component 204. The request can be to create a new product catalog, or to change or update an existing product catalog. The Maintain Catalog operation 210 is included in a Product Catalog Transmission Receiving In interface 214.

A Change Transmission Status operation 216 sends a product catalog transmission status change notification using a Change Product Catalog based on Published Product Catalog asynchronous inbound process agent 218 to update the Product Catalog master data object 106. For example, the operation 216 can send a change notification to update the Product Catalog master data object 106 if input is received from the Product Catalog Publishing process component 124. The change notification can be to update the status of a catalog publication transmission package sent out earlier.

A Change Publication Status operation 220 sends a product catalog publication status change using the Change Product Catalog based on Published Product Catalog asynchronous inbound process agent 218 to update the Product Catalog master data object 106. For example, the operation 220 can send a change notification to update the Product Catalog master data object 106 if input is received from the Product Catalog Publishing process component 124. The change notification can be to set the result status of an ongoing catalog publication transmission.

A Change Catalog based on Publication Cancellation operation 222 sends a product catalog change notification using the Change Product Catalog based on Published Product Catalog asynchronous inbound process agent 218 to update the Product Catalog master data object 106. For example, the operation 222 can send a change notification to update the Product Catalog master data object 106 if input is received from the Product Catalog Publishing process component 124. The change notification can be to update a catalog based on the cancellation of publication.

A Change Catalog based on Item Lock Status operation 224 sends a product catalog change notification using the Change Product Catalog based on Published Product Catalog asynchronous inbound process agent 218 to update the Product Catalog master data object 106. For example, the operation 224 can send a change notification to update the Product Catalog master data object 106 if input is received from the Product Catalog Publishing process component 124. The change notification can be to change a product catalog based on the change of status of a locked item within the catalog.

A Change Catalog based on Content Change Publication Status operation 226 sends a product catalog change notification using the Change Product Catalog based on Published Product Catalog asynchronous inbound process agent 218 to update the Product Catalog master data object 106. For example, the operation 226 can send a change notification to update the Product Catalog master data object 106 if input is received from the Product Catalog Publishing process component 124. The change notification can be to change a catalog based on a change of status of a catalog publication.

The Change Transmission Status operation 216, the Change Publication Status operation 220, the Change Catalog based on Publication Cancellation operation 222, the Change Catalog based on Item Lock Status operation 224, and the Change Catalog based on Content Change Publication Status operation 226 are included in a Publishing In interface 228.

The Product Catalog master data object 106 can receive updated information and send the update into other components to perform further operations. As shown in FIG. 2B, multiple message agents can receive information from the Product Catalog master data object 106.

A Request Publication from Product Catalog to Product Catalog Publishing asynchronous outbound process agent 230 can invoke a Request Catalog Publication operation 232. For example, the outbound process agent 230 can send a request to publish a product catalog. The Request Publication from Product Catalog to Product Catalog Publishing asynchronous outbound process agent 230 can also invoke a Request Catalog Publication Cancellation operation 234. For example, the outbound process agent 230 can send a request to cancel publication of a product catalog. The Request Publication from Product Catalog to Product Catalog Publishing asynchronous outbound process agent 230 can also invoke a Request Catalog Item Lock operation 236. For example, the outbound process agent 230 can send a request to lock an item a product catalog. The Request Publication from Product Catalog to Product Catalog Publishing asynchronous outbound process agent 230 can also invoke a Request Catalog Publication Content Change operation 238. For example, the outbound process agent 230 can send a request to change the information for an item in a product catalog. The Request Catalog Publication operation 232, the Request Catalog Publication Cancellation operation 234, the Request Catalog Item Lock operation 236, and the Request Catalog Publication Content Change operation 238 are included in a Publishing Out interface 240.

A Notify of Publication from Product Catalog to Customer asynchronous outbound process agent 242 invokes a Notify of Catalog Update operation 244, which notifies another party (e.g., a customer) about a catalog publication. This can be a new catalog or an update to a previously published catalog. The Notify of Catalog Update operation 244 is included in a Transmission Sending Out interface 246. As an example, the operation 244 can then send a notification to the Product Catalog Authoring at Customer process component 208.

FIGS. 3A and 3B are block diagrams collectively showing the Product Catalog Publishing process component 124 (FIG. 1). For convenience in describing this process component, another process component is shown in the figures; this other process component is not part of the process component being described. This other process component is a Product Catalog Authoring process component 104. This other process component is used to represent software external to the process component in describing its interactions with the external software; however, while the external software can be implemented as such process components, this is not required.

A Maintain Published Product Catalog operation 304 can send a product catalog maintenance request using a Maintain Published Product Catalog asynchronous inbound process agent 306 to update the Published Product Catalog master data object 126. For example, the operation 304 can send a product catalog maintenance notification to update the Published Product Catalog master data object 126 if input is received from the Product Catalog Authoring process component 104. The maintenance notification can be to update the contents of a published catalog.

A Cancel Catalog Publication operation 308 can send a product catalog publication cancellation request using the Maintain Published Product Catalog asynchronous inbound process agent 306 to update the Published Product Catalog master data object 126. For example, the operation 308 can send a product catalog publication cancellation notification to update the Published Product Catalog master data object 126 if input is received from the Product Catalog Authoring process component 104. The maintenance notification can be to cancel the publication of a catalog.

A Lock Published Catalog Items operation 310 can send a product catalog item lock request using the Maintain Published Product Catalog asynchronous inbound process agent 306 to update the Published Product Catalog master data object 126. For example, the operation 310 can send a product catalog item lock notification to update the Published Product Catalog master data object 126 if input is received from the Product Catalog Authoring process component 104. The maintenance notification can be to place a lock on items within a published catalog.

A Change Published Catalog Content operation 312 can send a product catalog content change request using the Maintain Published Product Catalog asynchronous inbound process agent 306 to update the Published Product Catalog master data object 126. For example, the operation 312 can send a product catalog content change notification to update the Published Product Catalog master data object 126 if input is received from the Product Catalog Authoring process component 104. The maintenance notification can be to change the content of a published catalog.

The Maintain Published Product Catalog operation 304, the Cancel Catalog Publication operation 308, the Lock Published Catalog Items operation 310, and the Change Published Catalog Content operation 312 are included in a Publishing In interface 314.

The Published Product Catalog master data object 126 can receive updated information and send the update into other components to perform further operations. As shown in FIG. 3B, multiple process agents can receive information from the Published Product Catalog master data object 126.

A Notify of Product Catalog Publication Status asynchronous outbound process agent 316 can invoke a Notify of Publication Transmission Package Check operation 318. For example, the outbound process agent 316 can send a notification of a publication transmission package check. The Notify of Product Catalog Publication Status asynchronous outbound process agent 316 can also invoke a Confirm Catalog Publication operation 320. For example, the outbound process agent 316 can send a confirmation that a product catalog has been published. The Notify of Product Catalog Publication Status asynchronous outbound process agent 316 can also invoke a Confirm Catalog Publication Cancellation operation 322. For example, the outbound process agent 316 can send a confirmation that a product catalog publication has been cancelled. The Notify of Product Catalog Publication Status asynchronous outbound process agent 316 can also invoke a Confirm Catalog Item Lock operation 324. For example, the outbound process agent 316 can send a request to lock an item in a product catalog. The Notify of Product Catalog Publication Status asynchronous outbound process agent 316 can also invoke a Confirm Catalog Publication Content Change operation 326. For example, the outbound process agent 316 can send a request to change the information for an item in a product catalog. The Notify of Publication Transmission Package Check operation 318, the Confirm Catalog Publication operation 320, the Confirm Catalog Publication Cancellation operation 322, the Confirm Catalog Item Lock operation 324, and the Confirm Catalog Publication Content Change operation 326 are included in a Publishing Out interface 328.

The subject matter described in this specification and all of the functional operations described in this specification can be implemented in digital electronic circuitry, or in computer software, firmware, or hardware, including the structural means disclosed in this specification and structural equivalents thereof, or in combinations of them. The subject matter described in this specification can be implemented as one or more computer program products, i.e., one or more computer programs tangibly embodied in an information carrier, e.g., in a machine-readable storage device or in a propagated signal, for execution by, or to control the operation of, data processing apparatus, e.g., a programmable processor, a computer, or multiple computers. A computer program (also known as a program, software, software application, or code) can be written in any form of programming language, including compiled or interpreted languages, and it can be deployed in any form, including as a stand-alone program or as a module, component, subroutine, or other unit suitable for use in a computing environment. A computer program does not necessarily correspond to a file. A program can be stored in a portion of a file that holds other programs or data, in a single file dedicated to the program in question, or in multiple coordinated files (e.g., files that store one or more modules, sub-programs, or portions of code). A computer program can be deployed to be executed on one computer or on multiple computers at one site or distributed across multiple sites and interconnected by a communication network.

The processes and logic flows described in this specification can be performed by one or more programmable processors executing one or more computer programs to perform functions by operating on input data and generating output. The processes and logic flows can also be performed by, and apparatus can also be implemented as, special purpose logic circuitry, e.g., an FPGA (field programmable gate array) or an ASIC (application-specific integrated circuit).

Processors suitable for the execution of a computer program include, by way of example, both general and special purpose microprocessors, and any one or more processors of any kind of digital computer. Generally, a processor will receive instructions and data from a read-only memory or a random access memory or both. The essential elements of a computer are a processor for executing instructions and one or more memory devices for storing instructions and data. Generally, a computer will also include, or be operatively coupled to receive data from or transfer data to, or both, one or more mass storage devices for storing data, e.g., magnetic, magneto-optical disks, or optical disks. Information carriers suitable for embodying computer program instructions and data include all forms of non-volatile memory, including by way of example semiconductor memory devices, e.g., EPROM, EEPROM, and flash memory devices; magnetic disks, e.g., internal hard disks or removable disks; magneto-optical disks; and CD-ROM and DVD-ROM disks. The processor and the memory can be supplemented by, or incorporated in, special purpose logic circuitry.

To provide for interaction with a user, the subject matter described in this specification can be implemented on a computer having a display device, e.g., a CRT (cathode ray tube) or LCD (liquid crystal display) monitor, for displaying information to the user and a keyboard and a pointing device, e.g., a mouse or a trackball, by which the user can provide input to the computer. Other kinds of devices can be used to provide for interaction with a user as well; for example, feedback provided to the user can be any form of sensory feedback, e.g., visual feedback, auditory feedback, or tactile feedback; and input from the user can be received in any form, including acoustic, speech, or tactile input.

The subject matter described in this specification can be implemented in a computing system that includes a back-end component (e.g., a data server), a middleware component (e.g., an application server), or a front-end component (e.g., a client computer having a graphical user interface or a Web browser through which a user can interact with an implementation of the subject matter described herein), or any combination of such back-end, middleware, and front-end components. The components of the system can be interconnected by any form or medium of digital data communication, e.g., a communication network. Examples of communication networks include a local area network (“LAN”) and a wide area network (“WAN”), e.g., the Internet.

The computing system can include clients and servers. A client and server are generally remote from each other and typically interact through a communication network. The relationship of client and server arises by virtue of computer programs running on the respective computers and having a client-server relationship to each other.

While this specification contains many specifics, these should not be construed as limitations on the scope of the invention or of what may be claimed, but rather as an exemplification of preferred embodiments of the invention. Certain features that are described in this specification in the context of separate embodiments, may also be provided in combination in a single embodiment. Conversely, various features that are described in the context of a single embodiment may also be provided in multiple embodiments separately or in any suitable subcombination. Moreover, although features may be described above as acting in certain combinations and even initially claimed as such, one or more features from a claimed combination can in some cases be excised from the combination, and the claimed combination may be directed to a subcombination or variation of a subcombination.

The subject matter has been described in terms of particular variations, but other variations can be implemented and are within the scope of the following claims. For example, the actions recited in the claims can be performed in a different order and still achieve desirable results. As one example, the processes depicted in the accompanying figures do not necessarily require the particular order shown, or sequential order, to achieve desirable results. In certain implementations, multitasking and parallel processing may be advantageous. Other variations are within the scope of the following claims. 

1. A non-transitory computer readable storage medium including program code executed by a processor providing message-based services using a service-oriented methodology for implementing an instance of a catalog authoring deployment unit, the medium comprising: program code storing an instance of the catalog authoring deployment unit for defining, editing, and releasing product catalogs in an enterprise application, where the catalog authoring deployment unit defines the limits of an application-defined transaction for defining, editing, and releasing product catalogs by a set of actions that have atomicity, consistency, isolation, and durability in a database, and wherein the actions associated with the application-defined transaction are performed by at least one process component contained in the catalog authoring deployment unit, wherein each process component comprises a software package realizing a business process and exposing the process component's functionality as at least one service operation, wherein the catalog authoring deployment unit comprises: a maintain catalog operation operable to send a notification to update a product catalog, a change transmission status operable to send a notification to change the transmission status of a product catalog, a change publication status operation operable to send a notification to change the publication status of a product catalog, a change catalog based on publication cancellation operation operable to send a notification to update a product catalog based on a publication cancellation, a change catalog based on item lock status operation operable to send a notification to update a product catalog based on a locked item, a change catalog based on a content change publication status operation operable to send a notification to update a product catalog based on a catalog change content publication status, a request catalog publication operation operable to request that a product catalog be published, a request catalog publication cancellation operation operable to request a product catalog publication be cancelled, a request catalog item lock operation operable to request an item in a product catalog to be locked, a request catalog publication content change operation operable to request a content change in a product catalog publication, and a notify of catalog update operation operable to send a notification about an update to a product catalog; wherein the service operations of the catalog authoring deployment unit are packaged together to be deployed on a single computer system; program code executing the application-defined transaction for defining, editing, and releasing product catalogs in the enterprise application; and program code presenting data associated with the executed application-defined transaction for defining, editing, and releasing product catalogs in an enterprise application to a graphical user interface.
 2. The medium of claim 1, wherein the catalog authoring deployment unit further comprises a product catalog authoring process component.
 3. The medium of claim 2, wherein the product catalog authoring process component implements the maintain catalog operation, the change transmission status operation, the change publication status operation, the change catalog based on publication cancellation operation, the change catalog based on item lock status operation, the change catalog based on content change publication status operation, the request catalog publication operation, the request catalog publication cancellation operation, the request catalog item lock operation, the request catalog publication content change operation, and the notify of catalog update operation.
 4. The medium of claim 2, wherein the product catalog authoring process component comprises a product catalog master data object, a product catalog update run business object, a product catalog file upload run business object, a product catalog duplication run business object, a product catalog change list business object, a product catalog update method master data object, and a product catalog publishing sending run business object; wherein: the product catalog master data object is the business object responsible for the structured directory of catalog items where each catalog item represents a product and provides information about it; the product catalog update run business object is the business object responsible for the run to update product catalogs based on product catalog update methods; the product catalog file upload run business object is the business object responsible for the run to update a product catalog based on an uploaded file; the product catalog duplication run business object is the business object responsible for the run to copy a product catalog in total or in parts; the product catalog change list business object is the business object responsible for the list of changes to a product catalog; the product catalog update method master data object is the business object responsible for the set of rules controlling how products are cataloged in a product catalog and how to update the product catalog when cataloged products are changed; and the product catalog publishing sending run is the business object responsible for the run to trigger sending a product catalog for publication.
 5. The medium of claim 1, wherein the service operations are grouped into service interfaces, the service interfaces comprising: a product catalog transmission receiving in interface that includes the maintain catalog service operation; a publishing in interface that includes the change transmission status, the change publication status, the change catalog based on publication cancellation status, the change catalog based on item lock status, and the change catalog based on content change publication status service operations; a publishing out interface that includes the request catalog publication, the request catalog publication cancellation, the request catalog item lock, and the request catalog publication content change service operations; and a transmission sending out interface that includes the notify of catalog update service operation.
 6. The medium of claim 1, wherein the single computer system comprises a single physical hardware platform.
 7. A non-transitory computer readable storage medium including program code executed by a processor providing message-based services using a service-oriented methodology for implementing an instance of a catalog publishing deployment unit, the medium comprising: program code storing an instance of the catalog publishing deployment unit, where the catalog publishing deployment unit defines the limits of an application-defined transaction for providing released product catalogs for use in business processes by a set of actions that have atomicity, consistency, isolation, and durability in a database, and wherein the actions associated with the application-defined transaction are performed by at least one process component contained in the catalog publishing deployment unit, wherein each process component comprises a software package realizing a business process and exposing the process component's functionality as at least one service operation, wherein the catalog publishing deployment unit comprises: a maintain published product catalog operation operable to send a notification to update a published product catalog, a cancel catalog publication operation operable to send a notification to cancel the publication of a product catalog, a lock published catalog items operation operable to send a notification to lock items contained in a published product catalog, a change published catalog content operation operable to send a notification to change the content in a published product catalog, a notify of publication transmission package check operation operable to send a notification about a catalog publication transmission package check, a confirm catalog publication operation operable to send a notification to confirm the publication of a product catalog, a confirm catalog publication cancellation operation operable to send a notification to confirm the cancellation of a product catalog publication, a confirm catalog item lock operation operable to send a notification to confirm the lock of an item in a product catalog, and a confirm catalog publication content change operation operable to send a notification to confirm the content change of a product catalog publication; wherein the service operations of the catalog authoring deployment unit are packaged together to be deployed on a single computer system; program code executing the application-defined transaction for providing released product catalogs for use in business processes; and program code presenting data associated with the executed application-defined transaction for providing released product catalogs for use in business processes to a graphical user interface.
 8. The medium of claim 7, wherein the catalog publishing deployment unit further comprises a product catalog publishing process component.
 9. The medium of claim 8, wherein the product catalog publishing process component implements the maintain published product catalog operation, the cancel catalog publication operation, the lock published catalog items operation, the change published catalog content operation, the notify of publication transmission package check operation, the confirm catalog publication operation, the confirm catalog publication cancellation operation, the confirm catalog item lock operation, and the confirm catalog publication content change operation.
 10. The medium of claim 8, wherein the product catalog publishing process component comprises a published product catalog business object and a published product catalog update run business object, wherein: the published product catalog business object is a master data object representing a version of a product catalog that has been released for access by or exchange with the target group of people for whom the product catalog has been tailored; and the published product catalog update run business object represents a run to update a product catalog based on an uploaded file.
 11. The medium of claim 7, wherein the service operations are grouped into service interfaces, the service interfaces comprising: a publishing in interface that includes the maintain published product catalog, the cancel catalog publication, the lock published catalog items, and the change published catalog content service operations; and a publishing out interface that includes the notify of publication transmission package check, the confirm catalog publication, the confirm catalog publication cancellation, the confirm catalog item lock, and the confirm catalog publication content change service operations.
 12. The medium of claim 7, wherein the single computer system comprises a single physical hardware platform. 